-
Notifications
You must be signed in to change notification settings - Fork 840
Update storage-aws.md #2992
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update storage-aws.md #2992
Conversation
pracucci
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks! I would just suggest to link the blocks storage 🙏
docs/production/storage-aws.md
Outdated
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| Using just S3 is not an option, unless you use the experimental "blocks" | |
| storage engine. | |
| Using just S3 is not an option, unless you use the experimental [blocks storage engine](../blocks-storage/). |
|
@amckinley Would you mind fixing DCO please, so that we can merge this? You can also use |
pstibrany
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, with Marco's suggestion about the link.
docs/production/storage-aws.md
Outdated
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| Note that the choices for the chunks stoage backend are: "chunks" of | |
| Note that the choices for the chunks storage backend are: "chunks" of |
Improve clarity around blocks vs chunks storage options.
Signed-off-by: Marco Pracucci <marco@pracucci.com>
|
I'm taking over this PR to get it merged. |
Improve clarity around blocks vs chunks storage options.